Deprecate the 'include-externals' option. #3694
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I cannot see that this is used anywhere. We also have no tests for it. The documentation is minimal. It was added 8 years ago! How time flies!
I suspect this was put in place for Flutter, and Flutter switched to using the newer
--auto-include-dependencies
option.I want to remove it because the implementation looks slow. In
PackageBuilder._includedExternalsFrom
, we instantiate a newDartdocOptionContext
for every file analyzed. Maybe twice...Contribution guidelines:
dart format
.Note that many Dart repos have a weekly cadence for reviewing PRs - please allow for some latency before initial review feedback.